An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi everyone, I'm looking for advice from developers who have successfully navigated Guideline 4.3(b) Spam concerns. I've been building a custom marketplace platform called Goddess Destiny Psychics. The app includes custom advisor onboarding, advisor applications, identity verification, Stripe Connect onboarding, recorded readings, live chat functionality, advisor review workflows, admin moderation tools, automated approval/rejection processes, and a custom advisor evaluation system. My first submission was rejected under 4.3(b). A later submission also included a functionality concern, which I addressed. On my most recent submission, the functionality concern was no longer present, but the app was again rejected under 4.3(b). I've submitted an appeal because I believe the app contains substantial custom functionality and differs significantly from a simple template-based app. Has anyone successfully appealed a 4.3(b) rejection for a marketplace or service-based app? If so, what information was most helpful in demonstrating that your app was sufficiently differentiated? The review was completed in a relatively short amount of time, which left me concerned that some of the app's workflows may not have been fully evaluated. Thank you for any insights.

Hi everyone, I’m having an ongoing issue where my app submissions seem to sit in Waiting for Review for unusually long periods before Apple starts reviewing them. My current submission has been stuck in Waiting for Review since June 6 at 12:56 PM. This is not the first time this has happened. I’ve had previous submissions also take much longer than expected to even move into review. I understand review times can vary, but it seems like my app is repeatedly getting delayed at the Waiting for Review stage rather than actually being reviewed. I have not received a rejection, message, metadata issue, or request for more information. The submission just stays in the queue. Has anyone else experienced repeated delays like this? Is there anything in App Store Connect that can cause an app to keep getting stuck before review starts, such as subscription review, metadata, screenshots, compliance questions, app category, or account-level issues? Would the best next step be to contact Apple Developer Support, submit an App Review inquiry, or request an expedited review? Any advice would be appreciated.

Hi guys, I’m looking for some advice regarding App Review. I submitted my first app and it was rejected. I fixed the issues and submitted a new build. That review went through in a normal amount of time, but the app was rejected again for some additional issues. I fixed everything that was mentioned and submitted another build. The problem is that this one has now been sitting in “Waiting for Review” for 9 days, which feels a lot longer than the previous reviews. Has anyone else experienced this? Should I just keep waiting, or is there something I should do at this point? I thought about requesting an expedited review, but from what I understand Apple only grants those for things like critical bug fixes, time-sensitive launches, or urgent business needs, so I don’t think my case qualifies. Any insight would be appreciated. Thanks!

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. From 8th of June, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

I recently noticed that an app called Private Browsing Web Browser has been ranking at the top for the keyword “browser” on the App Store for a long time, even ahead of well-known browsers like Chrome, Firefox, and Safari. This is not only the case in the U.S.; it also appears to rank top in many other regions. This app has not been updated for a long time, and both its interface and feature set seem extremely basic. There also appears to be nobody to discuss it on the internet, and some of the App Store ratings look very suspicious. I previously reported this to the Apple team by email, and questioning about the algorithm, but they consistently responded: The App Store ranking system has no problem, and it's working as expected.” I wanted to ask everyone: Do you think it is normal for this app to rank number one for “browser” on the App Store? Also, the same developer has another very similar browser app called Snowbunny Private Web Browser, which also ranked high.

Hi everyone, I'm experiencing a frustrating situation with my app and hoping someone from Apple or the community can help or has faced the same. Situation: I configured two auto-renewable subscriptions (premium_monthly and premium_yearly) in App Store Connect under a subscription group Submitted them for review along with a new app build The app build was reviewed, accepted, and is now live on the App Store The subscriptions have been in "In Review" status for 20+ days with no action Impact: In production, StoreKit does not return the subscription products at all (as expected — Apple doesn't serve unreviewed products to StoreKit) Users cannot purchase subscriptions Monetization is completely blocked for a live, approved app What I've already tried: Submitted an expedited review request — no response Submitted a new app version update to force a combined review — app was approved again but subscriptions remain "In Review" Contacted App Store Support via the online form — no response after multiple days Cannot edit or resubmit the subscriptions because they are locked while "In Review" Technical details: Using Flutter with the official in_app_purchase package (v3.2.0) Implementation verified correct — prices load fine in sandbox/simulator Existing lifetime non-consumable (remove_ads_premium) is approved and working in production Only the two new subscriptions are stuck Questions: Is there any way to escalate a stuck subscription review beyond the standard expedited review form? Can I delete the subscriptions while they are "In Review" and recreate them, or will that cause issues with product ID reuse? Has anyone else experienced this and found a resolution? Any help or guidance from Apple engineers or fellow developers would be greatly appreciated. Thanks

I deleted Build 16 from the external Test Flight review approval because I want Build 17 to be used and set up for external review. I successfully removed it and it is not showing up under external testing.. but when I try to add my Build 17, it is greyed out and says that Build 16 is still waiting for review. Can you please fix this as soon as possible so I can begin the review process for my Build 17? Please let me know what information you may need. I'm hoping to get this resolved ASAP.

Hello everyone, I'm looking for advice from developers who may have encountered a similar situation. I originally submitted an app called Bien, which provides financial services and handles sensitive user data. During review, Apple rejected the app under Guideline 5.1.1 and advised that the app must be published under a seller/company name that reflects the Bien brand. Following that guidance, we went through the process of creating a new Apple Developer account under the appropriate company identity and submitted the app again using the new account. However, the new submission has now been rejected under Guideline 4.3(a) (Spam) because the binary, metadata, and concept are similar to apps submitted under another developer account. The challenge is that the similarities exist because it is the same app, being resubmitted under the new account that Apple previously indicated should be used. We have: Submitted a formal appeal. Opened a support case with Apple. Provided the previous review communication showing the requirement to publish under the Bien company name. Has anyone experienced a situation where an app was moved to a new developer account following Apple's ownership or branding requirements and subsequently received a 4.3(a) rejection? If so: How was the issue resolved? Was additional documentation required? Did App Review eventually recognize the account transition and approve the app? Any insights would be greatly appreciated. Thank you.

Hello App Review team - My app(App ID: 6756242440) is stuck in 'Waiting for review'. Once in a while updates are getting stuck like this, while other times same app reviews go through in 48 hours. Please help us understand any reasoning behind this so we can plan our development accordingly. Thanks in advance!

submitted a fun game bullseye beam 2 months ago, was in review for a month. uploaded new version and retried, still waiting for review after another week plus

Hi everyone, Our organization account has been stuck in review hell for almost 3 months now if you count the enrollment phase. Long story short, we got hit with a Guideline 2.3.1(a) rejection recently. We spent days cleaning up the entire codebase, stripped out all old/unnecessary libraries, and ran static analysis to make sure everything is completely standard. There is zero obfuscated code or dynamic execution now. We submitted this clean version (Build 9) 6 business days ago, but it's just sitting there in 'Waiting for Review'. No updates, no emails, nothing. This delay is seriously hurting our business operations and commercial launch. The active case ID for this issue is 102893875646. If any Apple moderator or representative here can ping the App Review team or escalate this internally, it would be a lifesaver. Thanks.

Hi there, my App is showing "Waiting for Review" over 1+ week later. Previous reviews on this app went through within 24 hours, so this is a clear outlier. I've submitted expedited review requests, replied via Resolution Center, contacted App Review via the support form, and called phone support — all with no response or no ability to help on their end. Has anyone gotten unstuck from a similar situation recently or are longer review times common currently? Appreciate any pointers.

Hi there, my app is still showing "Waiting for Review" over 1 week later. Previous reviews on this app went through within 24 hours, so this is a clear outlier. All prior reviewer feedback has been addressed in the current build. I've submitted expedited review requests, replied via Resolution Center, contacted App Review via the support form, and called phone support — all with no response or no ability to help on their end. Has anyone gotten unstuck from a similar situation recently? Appreciate any pointers.

Hi Everyone, Our app update has been in "Waiting for Review" status for over a week now, which is well beyond the usual review window. It has not yet moved to "In Review." Status: Waiting for Review (unchanged for 7+ days) Contains a critical production bug fix Our live users are currently affected by an issue, so getting this update through is fairly urgent. We have already submitted an expedited review request, but there has been no movement so far. Is anyone else experiencing unusually long "Waiting for Review" times recently? Any guidance on whether this is a known backlog, or anything we can do to help move this along, would be greatly appreciated.

Hello everyone, I would appreciate any advice or insight from developers who have experienced a similar situation. Our app, FORTIS HRIS, was submitted to App Review on May 19, 2026 and has been in "In Review" status since May 20, 2026. It has now been over 21 days without any update. App details: First app on our Apple Developer Organization account Internal HR application for FORTIS GARMENTS LTD. Features include attendance, leave management, payroll, employee directory, and geo-punch attendance Users cannot register themselves; only company employees can log in using company-issued credentials Working review credentials were provided in App Review Information No Resolution Center messages No requests for additional information No rejection Status remains "In Review" We have contacted Apple Developer Support multiple times and opened support cases, but have not yet received any update regarding the review. Has anyone experienced a similar delay with an employee-only business application? Is this normal for internal corporate apps, or should we be taking any additional action? Any guidance or shared experiences would be greatly appreciated. Thank you.

Hello, I am posting here because I no longer have access to the communication channels that were previously available to discuss my developer account with Apple. My appeal was denied, but Apple informed me that I could submit a reinstatement request after addressing the concerns that had been identified. Following that communication, I spent considerable time reviewing my applications, metadata, screenshots, codebase, user flows, and business practices. Although I do not believe my account was involved in dishonest or fraudulent activity, I nevertheless made extensive changes in an effort to address any potential concerns Apple may have had. The main difficulty is that the specific conduct that led to the termination decision was never clearly explained to me. Apple cited Section 3.2(f) and provided examples of prohibited behavior, but did not identify which specific action or activity was associated with my account. As a result, I was left attempting to correct every possible issue without understanding what the actual concern was. In addition, throughout my participation in the Apple Developer Program, I had never previously encountered a notice, suspension, or similar action of this nature. This made it even more difficult for me to understand what specific issue Apple believed had occurred and how best to address it. While I was still implementing changes and preparing what I believed would be a reinstatement submission, I received a termination notice. Since the termination, I have lost access to the Contact Us page and the communication channels that were previously available to me. I would therefore appreciate guidance from Apple or from developers who may have experienced a similar situation: How is a developer expected to submit a reinstatement request after termination if the Contact Us page is no longer accessible? Is there an alternative channel through which reinstatement requests can be submitted? Has anyone successfully submitted a reinstatement request after account termination and received a review? I am not asking Apple to reverse its decision through this forum. I am simply trying to understand how a developer is expected to submit a reinstatement request after termination when the previously available communication channels are no longer accessible. Thank you for your time.

Hi, My app "Stories for Two" has been approved and is ready for distribution, but it's blocked in all 27 EU countries because my DSA trader status has been stuck "In Review" since April 26, 2026 — over 6 weeks ago. I've already submitted all the required information. The "DAC7 Directive" line shows as Active, but "Digital Services Act" remains stuck in review with no way to action it from my side. Has anyone experienced this and found a fix? I've seen someone suggest canceling and resubmitting the review request — is that possible and if so, how exactly? Thanks! Boris

Hello, We are seeking guidance regarding our developer account, which is under a Pending Termination Notice under Section 3.2(f). We deeply respect the App Store Review Guidelines and the standards Apple sets to keep the ecosystem safe and trustworthy. We take these rules seriously and submitted an appeal to the App Review Board and, following our correspondence on May 29, provided a full set of additional corrective actions to address the issues identified and bring our products into full compliance — including a mandatory internal compliance process to ensure we meet Apple's standards going forward. It has now been about two weeks, and we have not yet received a response on these latest materials. We have an 8-year history as an Apple Developer Program member, and we want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team or the community on the best way to confirm our materials are under active review, and on any additional steps that would help. Thank you. Reference details: Case ID: 102900026351 Appeal Ticket: APL444296

Hello, I am requesting clarification from Apple engineers or or experienced developers regarding a potential App Store Connect review queue issue. Current status: App remains in “Waiting for Review” No transition to “In Review” at any point Timeline: Initial submission: May 28, 2026 Status has remained “Waiting for Review” since initial submission. Expedited review request: Approved by Apple Support but No visible change in App Store Connect status Support history: I have followed up multiple times (approximately 4 messages) through the same Apple Support case regarding this issue, but I have not yet received a response or clarification. Case reference: Case ID: 102907712466 At this point, I am trying to understand whether this behavior is expected or if there may be a queue assignment or processing issue preventing the submission from being picked up, even after expedited approval. Specifically: Is it normal for a submission to remain in “Waiting for Review” after expedited approval? Or could this indicate a processing or queue assignment issue in App Store Connect? Any clarification from Apple engineers or experienced developers would be greatly appreciated. Thank you.

Hi everyone, I’m facing an issue with the App Store review / support process and would really appreciate some guidance from others who may have experienced something similar. I have contacted Apple Developer Support multiple times regarding my app, but unfortunately I have not received any meaningful response so far. At this point, I am unsure how to move forward or how to get proper feedback to resolve the issue. The lack of response is making it difficult to proceed with my app submission and address any potential problems on Apple’s side. Has anyone encountered a similar situation? How did you successfully escalate the issue? Is there a specific way to get a response from the review team or developer support? Any advice on how to move forward would be highly appreciated. Thank you in advance!